When adding an existing server share as a DFS target, does it invalidate the local share path?
Hello,
We are beginning to implement DFS on our file servers (2008 R2 Std). We have had at least one instance where after adding an existing share (\\server\share) as a DFS target, the share became unreachable at \\server\share. During
this time, the share was accessible via the DFS namespace (\\domain\DFSroot\share). Is this expected behavior, or just a glitch?
Travis
June 3rd, 2011 6:24pm
its not expected behaviour. does that happen to all your shares? what error message do you get?
Free Windows Admin Tool Kit Click here and download it now
June 3rd, 2011 6:42pm
I wish I had a screenshot form when we were experiencing the issue. We have since rebuilt the namespace several times without issue. It was not the usual error for when a share does not exist, but more that the share was unavailable.
Since we have only seen this once, I'm not too worried about it. I just wanted to get a confirmation before putting this in production.
Thank you.
June 3rd, 2011 7:33pm